-
Notifications
You must be signed in to change notification settings - Fork 14k
[beta] backports #148591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[beta] backports #148591
Conversation
(cherry picked from commit 3d9c69b)
This commit fixes an accidental regression from 144678 where wasm targets would now accidentally use the wrong import module map for a symbol causing a symbol to skip mangling. This can result in compilation failures when symbols are used in cross-crate situations. Closes 148347 (cherry picked from commit 93fef45)
|
@bors r+ rollup=never |
|
💔 Test failed - checks-actions |
|
Hmm, NPM error in tidy, but it doesn't complain locally for me... @bors try jobs=tidy |
This comment has been minimized.
This comment has been minimized.
[beta] backports try-job: tidy
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test for 531eec0 failed: CI. Failed jobs:
|
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
@bors retry |
|
Scheduling: If rollups fail, prefer rollup=never over non-rolled-up iffy. @bors p=1 |
|
Actually, let's give this a fair chance to run before the next rollup. @bors p=5 |
|
☀️ Test successful - checks-actions |
wasm_import_moduleattribute cross-crate Fixwasm_import_moduleattribute cross-crate #148363r? cuviper